Estimating Application Size with Function Point Analysis

objects that represent common attributes are not visible to the user and do not relate to logical files themselves. They rather define a subgroup in each of their sub-objects. Concrete super-objects, visible to the user, are candidates for files. Their sub-objects can be visible to the user and are then candidates for files themselves. Otherwise, they are an optional subgroup of their super-object and will be represented as a RET for the file related to the super-object. a. Typed objects: 7a. Select every object of entity type as a candidate for a logical file, unless rules 9-11 state otherwise. 8a. No other objects will be selected. The documentation required for this step is the typed analysis (object) model. b. Un-typed objects 7b. Select every domain object as a candidate for a logical file, unless rules 9-11 state otherwise. 8b. No other objects will be selected. The documentation required for this step is the domain object model. Aggregation relationships: 9. A domain or entity object that is a part of another object (is aggregated into another object) is not a candidate for a logical file, but it is a candidate for a record element type (RET) for the file related to the aggregating top-level object. The documentation required for this step is the object model used under (a) or (b). For inheritance relationships: